Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1518

reference: 853-tree-1
name: 1518
tree-preservation-order: undefined
853-tpo-1
uprn
address-text
point: POINT (-0.969166 50.864876)
geometry: MULTIPOLYGON (((-0.969095 50.864868,-0.969098 50.864882,-0.969108 50.864895,-0.969124 50.864905,-0.969143 50.864911,-0.969165 50.864914,-0.969187 50.864912,-0.969207 50.864905,-0.969223 50.864896,-0.969233 50.864883,-0.969237 50.864869,-0.969234 50.864855,-0.969224 50.864843,-0.969209 50.864833,-0.969189 50.864826,-0.969167 50.864824,-0.969145 50.864826,-0.969125 50.864832,-0.969109 50.864842,-0.969099 50.864854,-0.969095 50.864868)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL